Una arquitectura para sistemas de ubicación

Los modelos de ubicación se desarrollan con el fin de expresar las relaciones físicas entre los objetos. Como todo modelo, puede ocurrir que surjan nuevos requerimientos luego de que este fue puesto en producción y que estos provoquen modificaciones en el modelo original. Dependiendo de cuán correcto y con qué fin fue diseñado, estos cambios pueden provocar que el modelo quede obsoleto y se tenga que rediseñar. Los modelos de ubicación existentes (Capítulo 2 y 3) son adecuados dependiendo del tipo de aplicación que estemos desarrollando. Por lo tanto debemos conocer con anterioridad cuales son los requerimientos que esta posee para tomar la decisión de cual de ellos elegir. Si tomamos en cuenta que con la aparición de los dispositivos móviles los requerimientos pueden ser aún más cambiantes y que los modelos de ubicaciones podrán ser utilizados por múltiples aplicaciones, es probable que en un tiempo menor al esperado nuestro modelo quede obsoleto. Los modelos actuales intentan modelar a la ubicación como algo formalizable lo cual provoca que los mecanismos para agregar semántica a las ubicaciones no sean tomados en cuenta. Por este motivo, el primer objetivo que tiene este trabajo es el de proveer un modelo que permita enriquecer semánticamente a las ubicaciones de manera que los problemas de escalabilidad encontrados en las implementaciones actuales desaparezcan. De esta manera se permitirá que un modelo evolucione agregando semántica mediante distintas representaciones de una misma ubicación.Facultad de Informátic

Una arquitectura para sistemas de ubicación

Los modelos de ubicación se desarrollan con el fin de expresar las relaciones físicas entre los objetos. Como todo modelo, puede ocurrir que surjan nuevos requerimientos luego de que este fue puesto en producción y que estos provoquen modificaciones en el modelo original. Dependiendo de cuán correcto y con qué fin fue diseñado, estos cambios pueden provocar que el modelo quede obsoleto y se tenga que rediseñar. Los modelos de ubicación existentes (Capítulo 2 y 3) son adecuados dependiendo del tipo de aplicación que estemos desarrollando. Por lo tanto debemos conocer con anterioridad cuales son los requerimientos que esta posee para tomar la decisión de cual de ellos elegir. Si tomamos en cuenta que con la aparición de los dispositivos móviles los requerimientos pueden ser aún más cambiantes y que los modelos de ubicaciones podrán ser utilizados por múltiples aplicaciones, es probable que en un tiempo menor al esperado nuestro modelo quede obsoleto. Los modelos actuales intentan modelar a la ubicación como algo formalizable lo cual provoca que los mecanismos para agregar semántica a las ubicaciones no sean tomados en cuenta. Por este motivo, el primer objetivo que tiene este trabajo es el de proveer un modelo que permita enriquecer semánticamente a las ubicaciones de manera que los problemas de escalabilidad encontrados en las implementaciones actuales desaparezcan. De esta manera se permitirá que un modelo evolucione agregando semántica mediante distintas representaciones de una misma ubicación.Facultad de Informátic

Agile managing of web requirements with WebSpec

Web application development is a complex and time consuming process that involves di erent stakeholders (ranging from customers to developers); these applications have some unique characteristics like navigational access to information, sophisticated interaction features, etc. However, there have been few proposals to represent those requirements that are speci c to Web applications. Consequently, validation of requirements (e.g. in acceptance tests) is usually informal, and as a result troublesome. To overcome these problems, this PhD Thesis proposes WebSpec, a domain speci c language for specifying the most relevant and characteristic requirements of Web applications: those involving interaction and navigation. We describe WebSpec diagrams, discussing their abstraction and expressive power. As part of this work, we have created a test driven model based approach called WebTDD that gives a good framework for the language. Using the language with this approach we have test several of its features such as automatic test generation, management of changes in requirements, and improving the understanding of the diagrams through application simulation. This PhD Thesis is composed of a set of published and submitted papers. In order to write this PhD Thesis as a collection of papers, several requirements must be taken into account as stated by the University of Alicante. With regard to the content of the PhD Thesis, it must speci cally include a summary which is devoted to the description of initial hypotheses, research objectives, and the collection of publications itself, thus justifying its coherence. It should be underlined that this summary of the PhD Thesis must also include research results and nal conclusions. This summary corresponds to part I of this PhD Thesis (chapter 1 has been written in Spanish while chapter 2 is in English). This work has been partially supported by the following projects: MANTRA (GV/2011/035) from Valencia Ministry, MANTRA (GRE09-17) from the University of Alicante and by the MESOLAP (TIN2010-14860) project from the Spanish Ministry of Education and Science.Este trabajo ha sido parcialmente financiado por los siguientes proyectos: Mantra (GV/2011/035), Ministerio de Valencia, MANTRA (GRE09-17) de la Universidad de Alicante y por el MESOLAP (TIN2010-14860) proyecto del Ministerio de Educación y Ciencia de España.Facultad de Informátic

Detecting Conflicts and Inconsistencies in Web Application Requirements

Web applications evolve fast. One of the main reasons for this evolution is that new requirements emerge and change constantly. These new requirements are posed either by customers or they are the consequence of users’ feedback about the application. One of the main problems when dealing with new requirements is their consistency in relationship with the current version of the application. In this paper we present an effective approach for detecting and solving inconsistencies and conflicts in web software requirements. We first characterize the kind of inconsistencies arising in web applications requirements and then show how to isolate them using a modeldriven approach. With a set of examples we illustrate our approach

Bridging test and model-driven approaches in web engineering

In the last years there has been a growing interest in agile methods and their integration into the so called "unified" approaches. In the field of Web Engineering, agile approaches such as test-driven development are appealing because of the very nature of Web applications, while model-driven approaches provide a less error-prone code derivation; however the integration of both approaches is not easy. In this paper, we present a method-independent approach to combine the agile, iterative and incremental style of test-driven development with the more formal, transformation-based model-driven Web engineering approaches. We focus not only in the development process but also in the evolution of the application, and show how tests can be transformed together with model refactoring. As a proof of concept we show an illustrative example using WebRatio, the WebML design tool.Publicado en Lecture Notes in Computer Science book series (LNCS, vol. 5648).Laboratorio de Investigación y Formación en Informática Avanzad

Modelling the Requirements of Rich Internet Applications in WebRe

In the last years, several Web methodological approaches were defined in order to support the systematic building of Web software. Together with the constant technological advances, these methods must be constantly improved to deal with a myriad of new feasible application features, such as those involving rich interaction features. Rich Internet Applications (RIA) are Web applications exhibiting interaction and interface features that are typical in desktop software. Some specific methodological resources are required to deal with these characteristics. This paper presents a solution for the treatment of Web Requirements in RIA development. For this aim we present WebRE+, a requirement metamodel that incorporates RIA features into the modelling repertoire. We illustrate our ideas with a meaningful example of a business intelligence application.Ministerio de Educación y Ciencia TIN2007-67843-C06-03Ministerio de Educación y Ciencia TIN2010-20057-C03-0

Capture and evolution of web requirements using WebSpec

Developing Web applications is a complex and time consuming process that involves different kind of people, ranging from customers to developers. Requirement artefacts play an important role as they are used by these people to perform their daily activities. However, state of the art in requirement management for Web applications disregards valuable features that tend to improve the development process, such as quick validation during elicitation, automatic requirement validation on the final application and useful change management support. To tackle these problems we introduce WebSpec, a requirement artefact for specifying interaction and navigation features in Web applications. We show its use through the development of an example application in the social networking area, and its implementation as an Eclipse plugin.Publicado en Lecture Notes in Computer Science book series (LNCS, vol. 6385).Facultad de Informátic

Capture and evolution of web requirements using WebSpec

Developing Web applications is a complex and time consuming process that involves different kind of people, ranging from customers to developers. Requirement artefacts play an important role as they are used by these people to perform their daily activities. However, state of the art in requirement management for Web applications disregards valuable features that tend to improve the development process, such as quick validation during elicitation, automatic requirement validation on the final application and useful change management support. To tackle these problems we introduce WebSpec, a requirement artefact for specifying interaction and navigation features in Web applications. We show its use through the development of an example application in the social networking area, and its implementation as an Eclipse plugin.Publicado en Lecture Notes in Computer Science book series (LNCS, vol. 6385).Facultad de Informátic

Detecting Conflicts and Inconsistencies in Web Application Requirements

Web applications evolve fast. One of the main reasons for this evolution is that new requirements emerge and change constantly. These new requirements are posed either by customers or they are the consequence of users' feedback about the application. One of the main problems when dealing with new requirements is their consistency in relationship with the current version of the application. In this paper we present an effective approach for detecting and solving inconsistencies and conflicts in web software requirements. We first characterize the kind of inconsistencies arising in web applications requirements and then show how to isolate them using a model-driven approach. With a set of examples we illustrate our approach.Publicado en Lecture Notes in Computer Science book series (LNCS, vol. 7059).Laboratorio de Investigación y Formación en Informática Avanzad

Detecting Conflicts and Inconsistencies in Web Application Requirements

Web applications evolve fast. One of the main reasons for this evolution is that new requirements emerge and change constantly. These new requirements are posed either by customers or they are the consequence of users' feedback about the application. One of the main problems when dealing with new requirements is their consistency in relationship with the current version of the application. In this paper we present an effective approach for detecting and solving inconsistencies and conflicts in web software requirements. We first characterize the kind of inconsistencies arising in web applications requirements and then show how to isolate them using a model-driven approach. With a set of examples we illustrate our approach.Publicado en Lecture Notes in Computer Science book series (LNCS, vol. 7059).Laboratorio de Investigación y Formación en Informática Avanzad